-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: filter sub multiplexing #1048
Conversation
Thank you for opening this pull request! We require pull request titles and commits to follow the Conventional Commits specification and it looks like your PR needs to be adjusted. Details:
|
Jenkins BuildsClick to see older builds (25)
|
5e61d2b
to
b3eadd4
Compare
e097efe
to
883a58c
Compare
883a58c
to
295b509
Compare
9ba0298
to
bafbc2f
Compare
bafbc2f
to
f74d74f
Compare
Note that i am not fixing the conventional commits CI error for now, rather while merging it to master..committs will be squashed and i will fix commit messages then :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work!
As part of status-im/status-go#4665, Filter Management complexities are being moved within go-waku. This is part of larger reliability for req-resp protocols milestone.
This PR captures mainly following:
Note that rest of the items would be take up in a separate PR such as optimizing filter-ping and Filter peer connectivity maintenance.